Systems and methods of alarm triggered equipment verification using drone deployment of sensors

ABSTRACT

An equipment monitoring system includes an unmanned vehicle, an alarm circuit remote from the unmanned vehicle, and a vehicle control circuit remote from the unmanned vehicle. The unmanned vehicle can include a communications circuit and a flight controller. The alarm circuit detects a failure condition of a building component and outputs an indication of the failure condition. The vehicle control circuit receives the indication of the failure condition from the alarm circuit; generates, based on the indication of the failure condition, an equipment verification signal that includes an identifier of the building component, a position of the building component, and a test of the building component to be executed; and transmits the equipment verification signal to the flight controller of the unmanned vehicle via the communications circuit of the unmanned vehicle to cause the unmanned vehicle to execute the test of the building component.

BACKGROUND

Commercial buildings typically using large building control systems suchas fire detection systems, heating, ventilation, and air conditioning(HVAC) systems, access control systems, and video surveillance systems.

SUMMARY

One implementation of the present disclosure is an equipment monitoringsystem. The equipment monitoring system includes an unmanned vehicle, analarm circuit remote from the unmanned vehicle, and a vehicle controlcircuit remote from the unmanned vehicle. The unmanned vehicle includinga communications circuit and a flight controller. The alarm circuitdetects a failure condition of a building component and outputs anindication of the failure condition. The vehicle control circuitreceives the indication of the failure condition from the alarm circuit;generates, based on the indication of the failure condition, anequipment verification signal that includes an identifier of thebuilding component, a position of the building component, and a test ofthe building component to be executed; and transmits the equipmentverification signal to the flight controller of the unmanned vehicle viathe communications circuit of the unmanned vehicle to cause the unmannedvehicle to execute the test of the building component.

Another implementation of the present disclosure is a method of alarmtriggered equipment verification using drone deployment of sensors. Themethod includes detecting, by an alarm circuit remote from an unmannedvehicle, a failure condition of a building component; outputting, by thealarm circuit to a vehicle control circuit remote from the unmannedvehicle, an indication of the failure condition; generating, by thevehicle control circuit based on the indication of the alarm condition,an equipment verification signal that includes an identifier of thebuilding component, a position of the building component, and a test ofthe building component to be executed; and transmitting, by the vehiclecontrol circuit to a flight controller of the unmanned vehicle via acommunications circuit of the unmanned vehicle, the equipmentverification signal to cause the unmanned vehicle to execute the test ofthe building component.

Another implementation of the present disclosure is a vehicle controlcircuit including one or more processors and a non-transitoryprocessor-executable medium storing processor-readable instructions. Theinstructions, when executed by the one or more processors, cause the oneor more processors to receive, from an alarm circuit remote from anunmanned vehicle, an indication of an alarm condition regarding abuilding component; generate, based on the indication of the alarmcondition, an equipment verification signal that includes an identifierof the building component; and output, to a flight controller of theunmanned vehicle via a communications circuit of the unmanned vehicle,the equipment verification signal to cause the unmanned vehicle toexecute a test of the building component.

Those skilled in the art will appreciate that the summary isillustrative only and is not intended to be in any way limiting. Otheraspects, inventive features, and advantages of the devices and/orprocesses described herein, as defined solely by the claims, will becomeapparent in the detailed description set forth herein and taken inconjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a drawing of a building equipped with a HVAC system, accordingto an exemplary embodiment.

FIG. 2 is a schematic diagram of a waterside system which may be used inconjunction with the building of FIG. 1, according to an exemplaryembodiment.

FIG. 3 is a schematic diagram of an airside system which may be used inconjunction with the building of FIG. 1, according to an exemplaryembodiment.

FIG. 4 is a block diagram of a building management system (BMS) whichmay be used to monitor and control the building of FIG. 1, according toan exemplary embodiment.

FIG. 5 is a block diagram of an equipment verification system, accordingto an exemplary embodiment.

FIG. 6 is a flow diagram of a method of alarm triggered equipmentverification using drone deployment of sensors, according to anexemplary embodiment.

DETAILED DESCRIPTION Overview

The present disclosure relates generally to the field of HVAC systems,and more particularly to systems and methods of alarm triggeredequipment verification using drone deployment of sensors. Referringgenerally to the Figures, an equipment monitoring system includes anunmanned vehicle, an alarm circuit remote from the unmanned vehicle, anda vehicle control circuit remote from the unmanned vehicle. The unmannedvehicle including a communications circuit and a flight controller. Thealarm circuit detects a failure condition of a building component andoutputs an indication of the failure condition. The vehicle controlcircuit receives the indication of the failure condition from the alarmcircuit; generates, based on the indication of the failure condition, anequipment verification signal that includes an identifier of thebuilding component, a position of the building component, and a test ofthe building component to be executed; and transmits the equipmentverification signal to the flight controller of the unmanned vehicle viathe communications circuit of the unmanned vehicle to cause the unmannedvehicle to execute the test of the building component. For example, theunmanned vehicle can travel to within a proximity of the buildingcomponent, and use a sensor to execute the test of the buildingcomponent to receive sensor data that can be used to evaluate the testof the building component, and thus to verify if the building componentis in the failure condition (such that it is appropriate for the alarmcircuit to indicate that the building component is in an alarm state) orto determine that the failure condition is not present and an alarmshould be discontinued.

The present solution can improve upon existing equipment verificationsystems by enabling more rapid and accurate alarm conditionverification, including in conditions where existing verificationmethods may be limited due to environmental factors such as location,heat, and presence of gases.

Building Management System and HVAC System

Referring now to FIGS. 1-4, an exemplary building management system(BMS) and HVAC system in which the systems and methods of the presentdisclosure can be implemented is depicted. Referring particularly toFIG. 1, a perspective view of a building 10 is shown. Building 10 isserved by a BMS. A BMS is, in general, a system of devices that cancontrol, monitor, and manage equipment in or around a building orbuilding area. A BMS can include, for example, a HVAC system, a securitysystem, a lighting system, a fire alerting system, any other system thatis capable of managing building functions or devices, or any combinationthereof.

The BMS that serves building 10 includes an HVAC system 100. HVAC system100 can include a plurality of HVAC devices (e.g., heaters, chillers,air handling units, pumps, fans, thermal energy storage, etc.) thatprovide heating, cooling, ventilation, or other services for building10. For example, HVAC system 100 is shown to include a waterside system120 and an airside system 130. Waterside system 120 can provide a heatedor chilled fluid to an air handling unit of airside system 130. Airsidesystem 130 can use the heated or chilled fluid to heat or cool anairflow provided to building 10. An exemplary waterside system andairside system which can be used in HVAC system 100 are described ingreater detail with reference to FIGS. 2-3.

HVAC system 100 is shown to include a chiller 102, a boiler 104, and arooftop air handling unit (AHU) 106. Waterside system 120 can use boiler104 and chiller 102 to heat or cool a working fluid (e.g., water,glycol, etc.) and can circulate the working fluid to AHU 106. In variousembodiments, the HVAC devices of waterside system 120 can be located inor around building 10 (as shown in FIG. 1) or at an offsite locationsuch as a central plant (e.g., a chiller plant, a steam plant, a heatplant, etc.). The working fluid can be heated in boiler 104 or cooled inchiller 102, depending on whether heating or cooling is required inbuilding 10. Boiler 104 can add heat to the circulated fluid, forexample, by burning a combustible material (e.g., natural gas) or usingan electric heating element. Chiller 102 can place the circulated fluidin a heat exchange relationship with another fluid (e.g., a refrigerant)in a heat exchanger (e.g., an evaporator) to absorb heat from thecirculated fluid. The working fluid from chiller 102 and/or boiler 104can be transported to AHU 106 via piping 108.

AHU 106 can place the working fluid in a heat exchange relationship withan airflow passing through AHU 106 (e.g., via one or more stages ofcooling coils and/or heating coils). The airflow can be, for example,outside air, return air from within building 10, or a combination ofboth. AHU 106 can transfer heat between the airflow and the workingfluid to provide heating or cooling for the airflow. For example, AHU106 can include one or more fans or blowers that pass the airflow overor through a heat exchanger containing the working fluid. The workingfluid can then return to chiller 102 or boiler 104 via piping 110.

Airside system 130 can deliver the airflow supplied by AHU 106 (i.e.,the supply airflow) to building 10 via air supply ducts 112 and canprovide return air from building 10 to AHU 106 via air return ducts 114.In some embodiments, airside system 130 includes multiple variable airvolume (VAV) units 116. For example, airside system 130 is shown toinclude a separate VAV unit 116 on each floor or zone of building 10.VAV units 116 can include dampers or other flow control elements thatcan be operated to control an amount of the supply airflow provided toindividual zones of building 10. In some embodiments, airside system 130delivers the supply airflow into one or more zones of building 10 (e.g.,via supply ducts 112) without using intermediate VAV units 116 or otherflow control elements. AHU 106 can include various sensors (e.g.,temperature sensors, pressure sensors, etc.) that measure attributes ofthe supply airflow. AHU 106 can receive input from sensors locatedwithin AHU 106 and/or within the building zone and can adjust the flowrate, temperature, or other attributes of the supply airflow through AHU106 to achieve setpoint conditions for the building zone.

Referring now to FIG. 2, a block diagram of a waterside system 200 isdepicted. In various embodiments, waterside system 200 can supplement orreplace waterside system 120 in HVAC system 100 or can be implementedseparate from HVAC system 100. When implemented in HVAC system 100,waterside system 200 can include a subset of the HVAC devices in HVACsystem 100 (e.g., boiler 104, chiller 102, pumps, valves, etc.) and canoperate to supply a heated or chilled fluid to AHU 106. The HVAC devicesof waterside system 200 can be located within building 10 (e.g., ascomponents of waterside system 120) or at an offsite location such as acentral plant.

In FIG. 2, waterside system 200 is depicted as a central plant having aplurality of subplants 202-212. Subplants 202-212 are shown to include aheater subplant 202, a heat recovery chiller subplant 204, a chillersubplant 206, a cooling tower subplant 208, a hot thermal energy storage(TES) subplant 210, and a cold thermal energy storage (TES) subplant212. Subplants 202-212 consume resources (e.g., water, natural gas,electricity, etc.) from utilities to serve the thermal energy loads(e.g., hot water, cold water, heating, cooling, etc.) of a building orcampus. For example, heater subplant 202 can heat water in a hot waterloop 214 that circulates the hot water between heater subplant 202 andbuilding 10. Chiller subplant 206 can chill water in a cold water loop216 that circulates the cold water between chiller subplant 206 building10. Heat recovery chiller subplant 204 can transfer heat from cold waterloop 216 to hot water loop 214 to provide additional heating for the hotwater and additional cooling for the cold water. Condenser water loop218 can absorb heat from the cold water in chiller subplant 206 andreject the absorbed heat in cooling tower subplant 208 or transfer theabsorbed heat to hot water loop 214. Hot TES subplant 210 and cold TESsubplant 212 can store hot and cold thermal energy, respectively, forsubsequent use.

Hot water loop 214 and cold water loop 216 can deliver the heated and/orchilled water to air handlers located on the rooftop of building 10(e.g., AHU 106) or to individual floors or zones of building 10 (e.g.,VAV units 116). The air handlers push air past heat exchangers (e.g.,heating coils or cooling coils) through which the water flows to provideheating or cooling for the air. The heated or cooled air can bedelivered to individual zones of building 10 to serve the thermal energyloads of building 10. The water then returns to subplants 202-212 toreceive further heating or cooling.

Although subplants 202-212 are shown and described as heating andcooling water for circulation to a building, it is understood that anyother type of working fluid (e.g., glycol, CO2, etc.) can be used inplace of or in addition to water to serve the thermal energy loads. Insome embodiments, subplants 202-212 can provide heating and/or coolingdirectly to the building or campus without requiring an intermediateheat transfer fluid. These and other variations to waterside system 200are within the teachings of the present invention.

Each of subplants 202-212 can include a variety of equipment that canfacilitate the functions of the subplant. For example, heater subplant202 is shown to include a plurality of heating elements 220 (e.g.,boilers, electric heaters, etc.) that add heat to the hot water in hotwater loop 214. Heater subplant 202 is also shown to include severalpumps 222 and 224 that circulate the hot water in hot water loop 214 andto control the flow rate of the hot water through individual heatingelements 220. Chiller subplant 206 is shown to include a plurality ofchillers 232 that remove heat from the cold water in cold water loop216. Chiller subplant 206 is also shown to include several pumps 234 and236 that circulate the cold water in cold water loop 216 and control theflow rate of the cold water through individual chillers 232.

Heat recovery chiller subplant 204 is shown to include a plurality ofheat recovery heat exchangers 226 (e.g., refrigeration circuits) thatcan transfer heat from cold water loop 216 to hot water loop 214. Heatrecovery chiller subplant 204 is also shown to include several pumps 228and 230 that can circulate the hot water and/or cold water through heatrecovery heat exchangers 226 and to control the flow rate of the waterthrough individual heat recovery heat exchangers 226. Cooling towersubplant 208 is shown to include a plurality of cooling towers 238 thatcan remove heat from the condenser water in condenser water loop 218.Cooling tower subplant 208 is also shown to include several pumps 240that can circulate the condenser water in condenser water loop 218 andto control the flow rate of the condenser water through individualcooling towers 238.

Hot TES subplant 210 is shown to include a hot TES tank 242 that canstore the hot water for later use. Hot TES subplant 210 can also includeone or more pumps or valves that can control the flow rate of the hotwater into or out of hot TES tank 242. Cold TES subplant 212 is shown toinclude cold TES tanks 244 that can store the cold water for later use.Cold TES subplant 212 can also include one or more pumps or valves thatcan control the flow rate of the cold water into or out of cold TEStanks 244.

In some embodiments, one or more of the pumps in waterside system 200(e.g., pumps 222, 224, 228, 230, 234, 236, and/or 240) or pipelines inwaterside system 200 include an isolation valve associated therewith.Isolation valves can be integrated with the pumps or positioned upstreamor downstream of the pumps to control the fluid flows in watersidesystem 200. In various embodiments, waterside system 200 can includemore, fewer, or different types of devices and/or subplants based on theparticular configuration of waterside system 200 and the types of loadsserved by waterside system 200.

Referring now to FIG. 3, a block diagram of an airside system 300 isdepicted. In various embodiments, airside system 300 can supplement orreplace airside system 130 in HVAC system 100 or can be implementedseparate from HVAC system 100. When implemented in HVAC system 100,airside system 300 can include a subset of the HVAC devices in HVACsystem 100 (e.g., AHU 106, VAV units 116, ducts 112-114, fans, dampers,etc.) and can be located in or around building 10. Airside system 300can operate to heat or cool an airflow provided to building 10 using aheated or chilled fluid provided by waterside system 200.

In FIG. 3, airside system 300 is depicted to include an economizer-typeair handling unit (AHU) 302. Economizer-type AHUs vary the amount ofoutside air and return air used by the air handling unit for heating orcooling. For example, AHU 302 can receive return air 304 from buildingzone 306 via return air duct 308 and can deliver supply air 310 tobuilding zone 306 via supply air duct 312. In some embodiments, AHU 302is a rooftop unit located on the roof of building 10 (e.g., AHU 106 asdepicted in FIG. 1) or otherwise positioned to receive both return air304 and outside air 314. AHU 302 can be that can operate exhaust airdamper 316, mixing damper 318, and outside air damper 320 to control anamount of outside air 314 and return air 304 that combine to form supplyair 310. Any return air 304 that does not pass through mixing damper 318can be exhausted from AHU 302 through exhaust damper 316 as exhaust air322.

Each of dampers 316-320 can be operated by an actuator. For example,exhaust air damper 316 can be operated by actuator 324, mixing damper318 can be operated by actuator 326, and outside air damper 320 can beoperated by actuator 328. Actuators 324-328 can communicate with an AHUcontroller 330 via a communications link 332. Actuators 324-328 canreceive control signals from AHU controller 330 and can provide feedbacksignals to AHU controller 330. Feedback signals can include, forexample, an indication of a current actuator or damper position, anamount of torque or force exerted by the actuator, diagnosticinformation (e.g., results of diagnostic tests performed by actuators324-328), status information, commissioning information, configurationsettings, calibration data, and/or other types of information or datathat can be collected, stored, or used by actuators 324-328. AHUcontroller 330 can be an economizer controller that can use one or morecontrol algorithms (e.g., state-based algorithms, extremum seekingcontrol (ESC) algorithms, proportional-integral (PI) control algorithms,proportional-integral-derivative (PID) control algorithms, modelpredictive control (MPC) algorithms, feedback control algorithms, etc.)to control actuators 324-328.

Still referring to FIG. 3, AHU 302 is shown to include a cooling coil334, a heating coil 336, and a fan 338 positioned within supply air duct312. Fan 338 can be that can force supply air 310 through cooling coil334 and/or heating coil 336 and provide supply air 310 to building zone306. AHU controller 330 can communicate with fan 338 via communicationslink 340 to control a flow rate of supply air 310. In some embodiments,AHU controller 330 controls an amount of heating or cooling applied tosupply air 310 by modulating a speed of fan 338.

Cooling coil 334 can receive a chilled fluid from waterside system 200(e.g., from cold water loop 216) via piping 342 and can return thechilled fluid to waterside system 200 via piping 344. Valve 346 can bepositioned along piping 342 or piping 344 to control a flow rate of thechilled fluid through cooling coil 334. In some embodiments, coolingcoil 334 includes multiple stages of cooling coils that can beindependently activated and deactivated (e.g., by AHU controller 330, byBMS controller 366, etc.) to modulate an amount of cooling applied tosupply air 310.

Heating coil 336 can receive a heated fluid from waterside system 200(e.g., from hot water loop 214) via piping 348 and can return the heatedfluid to waterside system 200 via piping 350. Valve 352 can bepositioned along piping 348 or piping 350 to control a flow rate of theheated fluid through heating coil 336. In some embodiments, heating coil336 includes multiple stages of heating coils that can be independentlyactivated and deactivated (e.g., by AHU controller 330, by BMScontroller 366, etc.) to modulate an amount of heating applied to supplyair 310.

Each of valves 346 and 352 can be controlled by an actuator. Forexample, valve 346 can be controlled by actuator 354 and valve 352 canbe controlled by actuator 356. Actuators 354-356 can communicate withAHU controller 330 via communications links 358-360. Actuators 354-356can receive control signals from AHU controller 330 and can providefeedback signals to controller 330. In some embodiments, AHU controller330 receives a measurement of the supply air temperature from atemperature sensor 362 positioned in supply air duct 312 (e.g.,downstream of cooling coil 334 and/or heating coil 336). AHU controller330 can also receive a measurement of the temperature of building zone306 from a temperature sensor 364 located in building zone 306.

In some embodiments, AHU controller 330 operates valves 346 and 352 viaactuators 354-356 to modulate an amount of heating or cooling providedto supply air 310 (e.g., to achieve a setpoint temperature for supplyair 310 or to maintain the temperature of supply air 310 within asetpoint temperature range). The positions of valves 346 and 352 affectthe amount of heating or cooling provided to supply air 310 by coolingcoil 334 or heating coil 336 and may correlate with the amount of energyconsumed to achieve a desired supply air temperature. AHU controller 330can control the temperature of supply air 310 and/or building zone 306by activating or deactivating coils 334-336, adjusting a speed of fan338, or a combination of both.

Still referring to FIG. 3, airside system 300 is depicted to include abuilding management system (BMS) controller 366 and a client device 368.BMS controller 366 can include one or more computer systems (e.g.,servers, supervisory controllers, subsystem controllers, etc.) thatserve as system level controllers, application or data servers, headnodes, or master controllers for airside system 300, waterside system200, HVAC system 100, and/or other controllable systems that servebuilding 10. BMS controller 366 can communicate with multiple downstreambuilding systems or subsystems (e.g., HVAC system 100, a securitysystem, a lighting system, waterside system 200, etc.) via acommunications link 370 according to like or disparate protocols (e.g.,LON, BACnet, etc.). In various embodiments, AHU controller 330 and BMScontroller 366 can be separate (as shown in FIG. 3) or integrated. In anintegrated implementation, AHU controller 330 can be a software moduleconfigured for execution by a processor of BMS controller 366.

In some embodiments, AHU controller 330 receives information from BMScontroller 366 (e.g., commands, setpoints, operating boundaries, etc.)and provides information to BMS controller 366 (e.g., temperaturemeasurements, valve or actuator positions, operating statuses,diagnostics, etc.). For example, AHU controller 330 can provide BMScontroller 366 with temperature measurements from temperature sensors362-364, equipment on/off states, equipment operating capacities, and/orany other information that can be used by BMS controller 366 to monitoror control a variable state or condition within building zone 306.

Client device 368 can include one or more human-machine interfaces orclient interfaces (e.g., graphical user interfaces, reportinginterfaces, text-based computer interfaces, client-facing web services,web servers that provide pages to web clients, etc.) for controlling,viewing, or otherwise interacting with HVAC system 100, its subsystems,and/or devices. Client device 368 can be a computer workstation, aclient terminal, a remote or local interface, or any other type of userinterface device. Client device 368 can be a stationary terminal or amobile device. For example, client device 368 can be a desktop computer,a computer server with a user interface, a laptop computer, a tablet, asmartphone, a PDA, or any other type of mobile or non-mobile device.Client device 368 can communicate with BMS controller 366 and/or AHUcontroller 330 via communications link 372.

Referring now to FIG. 4, a block diagram of a building management system(BMS) 400 is depicted. BMS 400 can be implemented in building 10 toautomatically monitor and control various building functions. BMS 400 isshown to include BMS controller 366 and a plurality of buildingsubsystems 428. Building subsystems 428 are shown to include a buildingelectrical subsystem 434, an information communication technology (ICT)subsystem 436, a security subsystem 438, a HVAC subsystem 440, alighting subsystem 442, a lift/escalators subsystem 432, and a firesafety subsystem 430. Building subsystems 428 can include arefrigeration subsystem, an advertising or signage subsystem, a cookingsubsystem, a vending subsystem, a printer or copy service subsystem, orany other type of building subsystem that uses controllable equipmentand/or sensors to monitor or control building 10. In some embodiments,building subsystems 428 include waterside system 200 and/or airsidesystem 300, as described with reference to FIGS. 2-3.

Each of building subsystems 428 can include any number of devices,controllers, and connections for completing its individual functions andcontrol activities. HVAC subsystem 440 can include many of the samecomponents as HVAC system 100, as described with reference to FIGS. 1-3.For example, HVAC subsystem 440 can include a chiller, a boiler, anynumber of air handling units, economizers, field controllers,supervisory controllers, actuators, temperature sensors, and otherdevices for controlling the temperature, humidity, airflow, or othervariable conditions within building 10. Lighting subsystem 442 caninclude any number of light fixtures, ballasts, lighting sensors,dimmers, or other devices that can controllably adjust the amount oflight provided to a building space. Security subsystem 438 can includeoccupancy sensors, video surveillance cameras, digital video recorders,video processing servers, intrusion detection devices, access controldevices and servers, or other security-related devices.

Still referring to FIG. 4, BMS controller 366 is shown to include acommunications interface 407 and a BMS interface 409. Interface 407 canfacilitate communications between BMS controller 366 and externalapplications (e.g., monitoring and reporting applications 422,enterprise control applications 426, remote systems and applications444, applications residing on client devices 448, etc.) for allowinguser control, monitoring, and adjustment to BMS controller 366 and/orsubsystems 428. Interface 407 can also facilitate communications betweenBMS controller 366 and client devices 448. BMS interface 409 canfacilitate communications between BMS controller 366 and buildingsubsystems 428 (e.g., HVAC, lighting security, lifts, powerdistribution, business, etc.).

Interfaces 407, 409 can be or include wired or wireless communicationsinterfaces (e.g., jacks, antennas, transmitters, receivers,transceivers, wire terminals, etc.) for conducting data communicationswith building subsystems 428 or other external systems or devices. Invarious embodiments, communications via interfaces 407, 409 can bedirect (e.g., local wired or wireless communications) or via acommunications network 446 (e.g., a WAN, the Internet, a cellularnetwork, etc.). For example, interfaces 407, 409 can include an Ethernetcard and port for sending and receiving data via an Ethernet-basedcommunications link or network. In another example, interfaces 407, 409can include a WiFi transceiver for communicating via a wirelesscommunications network. In another example, one or both of interfaces407, 409 can include cellular or mobile phone communicationstransceivers. In one embodiment, communications interface 407 is a powerline communications interface and BMS interface 409 is an Ethernetinterface. In some embodiments, both communications interface 407 andBMS interface 409 are Ethernet interfaces or are the same Ethernetinterface.

Still referring to FIG. 4, BMS controller 366 is shown to include aprocessing circuit 404 including a processor 406 and memory 408.Processing circuit 404 can be communicably connected to BMS interface409 and/or communications interface 407 such that processing circuit 404and the various components thereof can send and receive data viainterfaces 407, 409. Processor 406 can be implemented as a generalpurpose processor, an application specific integrated circuit (ASIC),one or more field programmable gate arrays (FPGAs), a group ofprocessing components, or other suitable electronic processingcomponents.

Memory 408 (e.g., memory, memory unit, storage device, etc.) can includeone or more devices (e.g., RAM, ROM, Flash memory, hard disk storage,etc.) for storing data and/or computer code for completing orfacilitating the various processes, layers and modules described in thepresent application. Memory 408 can be or include volatile memory ornon-volatile memory. Memory 408 can include database components, objectcode components, script components, or any other type of informationstructure for supporting the various activities and informationstructures described in the present application. According to anexemplary embodiment, memory 408 is communicably connected to processor406 via processing circuit 404 and includes computer code for executing(e.g., by processing circuit 404 and/or processor 406) one or moreprocesses described herein.

In some embodiments, BMS controller 366 is implemented within a singlecomputer (e.g., one server, one housing, etc.). In various embodimentsBMS controller 366 can be distributed across multiple servers orcomputers (e.g., that can exist in distributed locations). Further,while FIG. 4 shows applications 422 and 426 as existing outside of BMScontroller 366, in some embodiments, applications 422 and 426 can behosted within BMS controller 366 (e.g., within memory 408).

Still referring to FIG. 4, memory 408 is shown to include an enterpriseintegration layer 410, an automated measurement and validation (AM&V)layer 412, a demand response (DR) layer 414, a fault detection anddiagnostics (FDD) layer 416, an integrated control layer 418, and abuilding subsystem integration later 420. Layers 410-420 can receiveinputs from building subsystems 428 and other data sources, determineoptimal control actions for building subsystems 428 based on the inputs,generate control signals based on the optimal control actions, andprovide the generated control signals to building subsystems 428. Thefollowing paragraphs describe some of the general functions performed byeach of layers 410-420 in BMS 400.

Enterprise integration layer 410 can be serve clients or localapplications with information and services to support a variety ofenterprise-level applications. For example, enterprise controlapplications 426 can provide subsystem-spanning control to a graphicaluser interface (GUI) or to any number of enterprise-level businessapplications (e.g., accounting systems, user identification systems,etc.). Enterprise control applications 426 can provide configurationGUIs for configuring BMS controller 366. In some embodiments, enterprisecontrol applications 426 can work with layers 410-420 to optimizebuilding performance (e.g., efficiency, energy use, comfort, or safety)based on inputs received at interface 407 and/or BMS interface 409.

Building subsystem integration layer 420 can be manage communicationsbetween BMS controller 366 and building subsystems 428. For example,building subsystem integration layer 420 can receive sensor data andinput signals from building subsystems 428 and provide output data andcontrol signals to building subsystems 428. Building subsystemintegration layer 420 can also manage communications between buildingsubsystems 428. Building subsystem integration layer 420 translatecommunications (e.g., sensor data, input signals, output signals, etc.)across a plurality of multi-vendor/multi-protocol systems.

Demand response layer 414 can optimize resource usage (e.g., electricityuse, natural gas use, water use, etc.) and/or the monetary cost of suchresource usage in response to satisfy the demand of building 10. Theoptimization can be based on time-of-use prices, curtailment signals,energy availability, or other data received from utility providers,distributed energy generation systems 424, from energy storage 427(e.g., hot TES 242, cold TES 244, etc.), or from other sources. Demandresponse layer 414 can receive inputs from other layers of BMScontroller 366 (e.g., building subsystem integration layer 420,integrated control layer 418, etc.). The inputs received from otherlayers can include environmental or sensor inputs such as temperature,carbon dioxide levels, relative humidity levels, air quality sensoroutputs, occupancy sensor outputs, room schedules, and the like. Theinputs can also include inputs such as electrical use (e.g., expressedin kWh), thermal load measurements, pricing information, projectedpricing, smoothed pricing, curtailment signals from utilities, and thelike.

According to an exemplary embodiment, demand response layer 414 includescontrol logic for responding to the data and signals it receives. Theseresponses can include communicating with the control algorithms inintegrated control layer 418, changing control strategies, changingsetpoints, or activating/deactivating building equipment or subsystemsin a controlled manner. Demand response layer 414 can also includecontrol logic to determine when to utilize stored energy. For example,demand response layer 414 can determine to begin using energy fromenergy storage 427 just prior to the beginning of a peak use hour.

In some embodiments, demand response layer 414 includes a control modulethat can actively initiate control actions (e.g., automatically changingsetpoints) which minimize energy costs based on one or more inputsrepresentative of or based on demand (e.g., price, a curtailment signal,a demand level, etc.). In some embodiments, demand response layer 414uses equipment models to determine an optimal set of control actions.The equipment models can include, for example, thermodynamic modelsdescribing the inputs, outputs, and/or functions performed by varioussets of building equipment. Equipment models can represent collectionsof building equipment (e.g., subplants, chiller arrays, etc.) orindividual devices (e.g., individual chillers, heaters, pumps, etc.).

Demand response layer 414 can further include or draw upon one or moredemand response policy definitions (e.g., databases, XML, files, etc.).The policy definitions can be edited or adjusted by a user (e.g., via agraphical user interface) so that the control actions initiated inresponse to demand inputs can be tailored for the user's application,desired comfort level, particular building equipment, or based on otherconcerns. For example, the demand response policy definitions canspecify which equipment can be turned on or off in response toparticular demand inputs, how long a system or piece of equipment shouldbe turned off, what setpoints can be changed, what the allowable setpoint adjustment range is, how long to hold a high demand setpointbefore returning to a normally scheduled setpoint, how close to approachcapacity limits, which equipment modes to utilize, the energy transferrates (e.g., the maximum rate, an alarm rate, other rate boundaryinformation, etc.) into and out of energy storage devices (e.g., thermalstorage tanks, battery banks, etc.), and when to dispatch on-sitegeneration of energy (e.g., via fuel cells, a motor generator set,etc.).

Integrated control layer 418 can use the data input or output ofbuilding subsystem integration layer 420 and/or demand response later414 to make control decisions. Due to the subsystem integration providedby building subsystem integration layer 420, integrated control layer418 can integrate control activities of the subsystems 428 such that thesubsystems 428 behave as a single integrated supersystem. In anexemplary embodiment, integrated control layer 418 includes controllogic that uses inputs and outputs from a plurality of buildingsubsystems to provide greater comfort and energy savings relative to thecomfort and energy savings that separate subsystems could provide alone.For example, integrated control layer 418 can use an input from a firstsubsystem to make an energy-saving control decision for a secondsubsystem. Results of these decisions can be communicated back tobuilding subsystem integration layer 420.

Integrated control layer 418 is shown to be logically below demandresponse layer 414. Integrated control layer 418 can enhance theeffectiveness of demand response layer 414 by enabling buildingsubsystems 428 and their respective control loops to be controlled incoordination with demand response layer 414. This configuration canreduce disruptive demand response behavior relative to conventionalsystems. For example, integrated control layer 418 can assure that ademand response-driven upward adjustment to the setpoint for chilledwater temperature (or another component that directly or indirectlyaffects temperature) does not result in an increase in fan energy (orother energy used to cool a space) that would result in greater totalbuilding energy use than was saved at the chiller.

Integrated control layer 418 can provide feedback to demand responselayer 414 so that demand response layer 414 checks that constraints(e.g., temperature, lighting levels, etc.) are properly maintained evenwhile demanded load shedding is in progress. The constraints can alsoinclude setpoint or sensed boundaries relating to safety, equipmentoperating limits and performance, comfort, fire codes, electrical codes,energy codes, and the like. Integrated control layer 418 is alsologically below fault detection and diagnostics layer 416 and automatedmeasurement and validation layer 412. Integrated control layer 418 canprovide calculated inputs (e.g., aggregations) to these higher levelsbased on outputs from more than one building subsystem.

Automated measurement and validation (AM&V) layer 412 can verify thatcontrol strategies commanded by integrated control layer 418 or demandresponse layer 414 are working properly (e.g., using data aggregated byAM&V layer 412, integrated control layer 418, building subsystemintegration layer 420, FDD layer 416, or otherwise). The calculationsmade by AM&V layer 412 can be based on building system energy modelsand/or equipment models for individual BMS devices or subsystems. Forexample, AM&V layer 412 can compare a model-predicted output with anactual output from building subsystems 428 to determine an accuracy ofthe model.

Fault detection and diagnostics (FDD) layer 416 can provide on-goingfault detection for building subsystems 428, building subsystem devices(i.e., building equipment), and control algorithms used by demandresponse layer 414 and integrated control layer 418. FDD layer 416 canreceive data inputs from integrated control layer 418, directly from oneor more building subsystems or devices, or from another data source. FDDlayer 416 can automatically diagnose and respond to detected faults. Theresponses to detected or diagnosed faults can include providing an alertmessage to a user, a maintenance scheduling system, or a controlalgorithm that can attempt to repair the fault or to work-around thefault.

FDD layer 416 can output a specific identification of the faultycomponent or cause of the fault (e.g., loose damper linkage) usingdetailed subsystem inputs available at building subsystem integrationlayer 420. In other exemplary embodiments, FDD layer 416 can provide“fault” events to integrated control layer 418 which executes controlstrategies and policies in response to the received fault events.According to an exemplary embodiment, FDD layer 416 (or a policyexecuted by an integrated control engine or business rules engine) canshut-down systems or direct control activities around faulty devices orsystems to reduce energy waste, extend equipment life, or assure propercontrol response.

FDD layer 416 can store or access a variety of different system datastores (or data points for live data). FDD layer 416 can use somecontent of the data stores to identify faults at the equipment level(e.g., specific chiller, specific AHU, specific terminal unit, etc.) andother content to identify faults at component or subsystem levels. Forexample, building subsystems 428 can generate temporal (i.e.,time-series) data indicating the performance of BMS 400 and the variouscomponents thereof. The data generated by building subsystems 428 caninclude measured or calculated values that exhibit statisticalcharacteristics and provide information about how the correspondingsystem or process (e.g., a temperature control process, a flow controlprocess, etc.) is performing in terms of error from its setpoint. Theseprocesses can be examined by FDD layer 416 to expose when the systembegins to degrade in performance and alert a user to repair the faultbefore it becomes more severe.

Systems and Methods of Alarm Triggered Equipment Verification UsingDrone Deployment of Sensors

Referring now to FIG. 5, a block diagram of an equipment monitoringsystem 500 is depicted. The equipment monitoring system 500 canincorporates features of the HVAC system 100, waterside system 200,airside system 300, and BMS 400. The equipment monitoring system 500includes an alarm circuit 510, a vehicle control circuit 520, and anunmanned vehicle 550. The vehicle control circuit 520 can receive anindication of an alarm condition of a building component 530 from thealarm circuit 510 and cause the unmanned vehicle 550 to move to aproximity of the building component 530 to verify the alarm condition.By remotely controlling the unmanned vehicle 550, the alarm circuit 510and vehicle control circuit 520 can more quickly and accurately verifyalarm conditions, including in situations where manual verification maynot be possible due to environmental factors such as location,temperature, and presence of fire, gases, or chemicals.

The alarm circuit 510 detects a failure condition of the buildingcomponent 530. The building component 530 can include any of variouscomponents described with respect to FIGS. 1-4, including but notlimited to components of HVAC system 100, waterside system 200, airsidesystem 300, or BMS 400. The alarm circuit 510 can be coupled to acomponent sensor 532 coupled to the building component 532. Thecomponent sensor 532 can output sensor information regarding thebuilding component 530, based on which the alarm circuit 510 detects thefailure condition, and can output an indication of the failurecondition. For example, the alarm circuit 510 can output the indicationof the failure condition to indicate a type of failure of the buildingcomponent 530 (e.g., temperature is out of range, smoke/fire is present,improper operation). The alarm circuit 510 can incorporate features ofFDD layer 416 described with reference to FIG. 4.

For example, the building component 530 can include a component of theHVAC system 100, such as chiller 102, and the component sensor 532 caninclude a temperature sensor that detects a temperature of the buildingcomponent 530. The alarm circuit 510 can evaluate a temperature alarmcondition based on the detected temperature and output the indication ofthe failure condition responsive to the detected temperature notsatisfying the temperature alarm condition (e.g., the detectedtemperature is greater than a predetermined threshold temperature atwhich the building component 530 is expected to be overheating).

The vehicle control circuit 520 includes a processing circuit 522 and acommunications circuit 524. The processing circuit 522 can incorporatefeatures of the processing circuit 404 described with reference to FIG.4. Communications circuit 524 can incorporate features of thecommunications interface 407 described with reference to FIG. 4.

The vehicle control circuit 520 receives the indication of the failurecondition from the alarm circuit 510. The vehicle control circuit 520transmit an equipment verification signal to the unmanned vehicle 550 tocause the unmanned vehicle 550 to execute a test of the buildingcomponent 530 based on the equipment verification signal. The equipmentverification signal can include an identifier of the building component530, which the vehicle control circuit 520 can extract from theindication of the failure condition. As discussed further below, thevehicle control circuit 520 can generate the equipment verificationsignal to include a position of the building component 530, and cangenerate the equipment verification signal to include a test of thebuilding component 530 to be executed by the unmanned vehicle.

The unmanned vehicle 550 can be an unmanned aerial vehicle, an unmannedland-based vehicle, a fixed wing vehicle, and/or a rotary wing vehicle.The unmanned vehicle 550 can be a drone. The unmanned vehicle 550includes a communications circuit 554 and a flight controller 558. Thecommunications circuit 554 can receive remote control signals. Forexample, the communications circuit 554 can receive the equipmentverification signal from the vehicle control circuit 520. Thecommunications circuit 554 can transmit data for receipt by remoteentities, such as the alarm circuit 510 and/or the vehicle controlcircuit 520.

The flight controller 558 controls movement of the unmanned vehicle 550,such as by controlling flight actuators, engine controllers, or othercomponents of the unmanned vehicle 550. The flight controller 558 caninclude an autopilot and/or an autothrottle. The unmanned vehicle 550can include a position sensor 560, and the flight controller 558 can useposition data received from the position sensor 560 to control movementof the unmanned vehicle 550. For example, the flight controller 558 canexecute a flight navigation function to move to the position of thebuilding component 530 based on information received from the positionsensor 560.

In some embodiments, the unmanned vehicle 550 includes a sensor circuit562. The sensor circuit 562 can be used to detect sensor data regardingthe building component 530. For example, the sensor circuit 562 candetect at least one of temperature data, pressure data, sound data, orlight data regarding the building component 530. The sensor circuit 562can include at least one of a temperature sensor, an infrared sensor, afire detector, a smoke detector, a light sensor, and a gas detector. Thesensor circuit 562 can include an image capture device that can detectone or more images of the building component 530. The sensor circuit 562can include an audio sensor that detects sound outputted by the buildingcomponent 530. The sensor circuit 562 can transmit a sensor signal basedon the detected sensor data to a remote entity, such as the alarmcircuit 510 and/or the vehicle control circuit 520. The sensor circuit562 can generate the sensor signal to include the detected sensor data(or a representation thereof). In some embodiments, the buildingcomponent 530 includes a detectable identifier (e.g., a QR code, an RFIDsignal), that the sensor circuit 562 can detect to confirm that thebuilding component 530 that the unmanned vehicle 550 is proximate to isthe building component 530 corresponding to the indication of thefailure condition.

As depicted in FIG. 5, the vehicle control circuit 520 and/or theunmanned vehicle 550 can include a verification circuit 570. Theverification circuit 570 can verify the indication of the failurecondition based on the sensor data received from the sensor circuit 562.The verification circuit 570 can analyze the sensor data to determinewhether the failure condition is verified. The verification circuit 570can output a verification signal indicating whether the failurecondition is verified responsive to verifying the indication of thefailure condition.

The verification circuit 570 can compare the sensor data to one or morethresholds corresponding to the failure condition, and verify thefailure condition based on the comparison. For example, if the failurecondition indicates that the building component 530 is in a failurealarm state if the temperature of the building component 530 is in apredetermined temperature range, the verification circuit 570 cancompare a temperature of the sensor data to the predeterminedtemperature range to determine whether the failure condition isverified. If the failure condition indicates that the building component530 is in a failure alarm state based on the presence of smoke, theverification circuit 570 can compare a smoke value (e.g., detectedconcentration of smoke particles) to a corresponding thresholdindicative of the presence of smoke to determine whether the failurecondition is verified.

In some embodiments, the verification circuit 570 verifies the failurecondition based on sound detected by the sensor circuit 562. Theverification circuit 570 can execute a frequency analysis of thedetected sound to identify one or more frequencies of the detectedsound. The verification circuit 570 can compare the identified one ormore frequencies to at least one of (1) a frequency template indicativeof the building component 530 being in the failure condition and (2) afrequency template indicative of the building component 530 not being inthe failure condition, and verify the failure condition based on thecomparison(s). For example, the verification circuit 570 may maintain adatabase indicating one or more predetermined frequencies at which thebuilding component 530 is understood to be operating normally, anddetermine the building component 530 to not be in the failure conditionresponsive to the identified one or frequencies matching the one or morepredetermined frequencies.

Functions executed by the verification circuit 570 may be distributedbetween the vehicle control circuit 520 and the unmanned vehicle 550based on computational requirements. For example, if the test of thebuilding component 530 is based on a temperature of the buildingcomponent 530, the verification circuit 570 may perform a test of thetemperature by comparing the temperature detected by the sensor circuit562 to at least one of an upper threshold limit or a lower thresholdlimit, which may be a relatively low demand test for the processinghardware of the verification circuit 570 to perform. If the test of thebuilding component 530 is based on a frequency analysis of audioreceived from the building component 530, the verification circuit 570can be executed by the vehicle control circuit 520, which may have arelatively greater computational capacity as compared to the processinghardware of the unmanned vehicle 550. As such, the size, weight, and/orpower requirements of unmanned vehicle 550 may be reduced withoutreducing the effectiveness of the system 500 in remotely verifyingfailure conditions of the building component 530.

In some embodiments, at least one of the vehicle control circuit 520 andthe verification circuit 570 includes a database 572. The database 572can assign each identifier of each building component 530 to acorresponding position of the building component 530. As such, thevehicle control circuit 520 can generate the equipment verificationsignal to include the corresponding position of the building component530 based on which the indication of the failure condition was received,and/or the verification circuit 570 can retrieve the correspondingposition from the database 572 to provide to the flight controller 558.In some embodiments, the database 572 maps predetermined routes to eachbuilding component 530, which the flight controller 558 can use tonavigate movement of the unmanned vehicle 550.

The database 572 can map each indication of each failure condition toone or more tests to be performed on the building component 530. Assuch, the vehicle control circuit 520 can generate the equipmentverification signal to include the test of the building component 530 tobe executed by the unmanned vehicle 550 and/or the verification circuit570 can retrieve the test to be executed from the database 572.

The unmanned vehicle 550 can improve upon existing systems by enablingverification of alarm conditions even in relatively harsh environmentalconditions. For example, the unmanned vehicle 550 can include at leastone of a heat sink 564 and a cooling system 566 to transport heat awayfrom temperature-sensitive components of the unmanned vehicle 550, suchas flight controller 558, sensor circuit 562, and/or verificationcircuit 570. In some embodiments, an operational temperature range ofthe unmanned vehicle 550 includes a temperature of at least 120 degreesFahrenheit. The operational temperature range may indicate a range atwhich sensor output by the unmanned vehicle 550 has an error rate lessthan a threshold error rate (e.g., in operation, the error rate of thesensor circuit 562 is no more than ten percent more than a nominal errorrate of the sensor circuit 562).

In response to receiving the verification signal, the alarm circuit 510can modify the alarm, such as by deactivating the alarm if theverification signal indicates that the failure condition does not exist,for example, if the building component 530 is in a normal alarm state.In some embodiments, the flight controller 558 causes the unmannedvehicle to return to a base station responsive to at least one of (1)the sensor circuit 562 completing the test of the building component 530and (2) the alarm circuit 510 modifying the alarm to be the normal alarmstate.

Referring now to FIG. 6, a method 600 of alarm triggered equipmentverification using drone deployment is depicted. The method 600 can beperformed using the system 500 described with reference to FIG. 5.

At 605, a failure condition of a building component is detected by analarm circuit. The alarm circuit can be coupled to an equipment sensorcoupled to the building component, and can detect the failure conditionbased on sensor data detected by the equipment sensor. The alarm circuitcan be remote from an unmanned vehicle.

At 610, the alarm circuit outputs an indication of the failurecondition. The alarm circuit can output the indication to a vehiclecontrol circuit remote from the unmanned vehicle. The alarm circuit canoutput a visual and/or audio alarm indicating the failure condition.

At 615, the vehicle control circuit generates an equipment verificationsignal based on the indication of the failure condition. The equipmentverification signal can include an identifier of the building component.The equipment verification signal can include a position of the buildingcomponent. The equipment verification signal can include a test of thebuilding component to be executed.

At 620, the equipment verification signal is transmitted to the unmannedvehicle. The equipment verification signal can cause the unmannedvehicle to execute the test, such as to cause a sensor circuit of theunmanned vehicle to execute the test. For example, the sensor circuitcan detect particular sensor data responsive to receiving the equipmentverification signal.

The construction and arrangement of the systems and methods as shown inthe various exemplary embodiments are illustrative only. Although onlyexample embodiments have been described in detail in this disclosure,many modifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, colors,orientations, etc.). For example, the position of elements can bereversed or otherwise varied and the nature or number of discreteelements or positions can be altered or varied. Accordingly, suchmodifications are intended to be included within the scope of thepresent disclosure. The order or sequence of any process or method stepscan be varied or re-sequenced according to alternative embodiments.Other substitutions, modifications, changes, and omissions can be madein the design, operating conditions and arrangement of the exemplaryembodiments without departing from the scope of the present disclosure.

References to “or” may be construed as inclusive so that any termsdescribed using “or” may indicate any of a single, more than one, andall of the described terms. References to at least one of a conjunctivelist of terms may be construed as an inclusive OR to indicate any of asingle, more than one, and all of the described terms. For example, areference to “at least one of ‘A’ and ‘B’” can include only ‘A’, only‘B’, as well as both ‘A’ and ‘B’. Such references used in conjunctionwith “comprising” or other open terminology can include additionalitems.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure may be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Combinationsof the above are also included within the scope of machine-readablemedia. Machine-executable instructions include, for example,instructions and data which cause a general purpose computer, specialpurpose computer, or special purpose processing machines to perform acertain function or group of functions.

Although the figures show a specific order of method steps, the order ofthe steps may differ from what is depicted. Also two or more steps maybe performed concurrently or with partial concurrence. Such variationwill depend on the software and hardware systems chosen and on designerchoice. All such variations are within the scope of the disclosure.Likewise, software implementations could be accomplished with standardprogramming techniques with rule based logic and other logic toaccomplish the various connection steps, processing steps, comparisonsteps and decision steps.

What is claimed is:
 1. An equipment monitoring system, comprising: anunmanned vehicle including a communications circuit and a flightcontroller; an alarm circuit remote from the unmanned vehicle, the alarmcircuit detects a failure condition of a building component and outputsan indication of the failure condition; and a vehicle control circuitremote from the unmanned vehicle, the vehicle control circuit: receivesthe indication of the failure condition from the alarm circuit;generates, based on the indication of the failure condition, anequipment verification signal that includes an identifier of thebuilding component, a position of the building component, and a test ofthe building component to be executed; and transmits the equipmentverification signal to the flight controller of the unmanned vehicle viathe communications circuit of the unmanned vehicle to cause the unmannedvehicle to execute the test of the building component.
 2. The equipmentmonitoring system of claim 1, comprising: a sensor circuit of theunmanned vehicle executes the test of the building component to detectsensor data regarding the building component and transmits a sensorsignal based on the sensor data to the vehicle control circuit.
 3. Theequipment monitoring system of claim 1, comprising: the unmanned vehicleincludes an image capture device that transmits at least one image ofthe building component to the vehicle control circuit.
 4. The equipmentmonitoring system of claim 1, comprising: the unmanned vehicle includesan audio sensor that detects audio information regarding the buildingcomponent.
 5. The equipment monitoring system of claim 1, comprising: atleast one of (1) a verification circuit of the unmanned vehicle and (2)the vehicle control circuit analyses sensor data detected by a sensorcircuit of the unmanned vehicle, and generates a verification signalindicating whether the failure condition is verified based on theanalyzed sensor data.
 6. The equipment monitoring system of claim 1,comprising: the unmanned vehicle includes at least one of a temperaturesensor, an infrared sensor, a fire detector, a smoke detector, a lightsensor, and a gas detector.
 7. The equipment monitoring system of claim1, comprising: an operational temperature range of the unmanned vehicleincludes a temperature of at least 120 degrees Fahrenheit.
 8. Theequipment monitoring system of claim 1, comprising: the unmanned vehiclereturns to a base station responsive to at least one of (1) completingthe test of the building component and (2) the alarm circuit indicatingthe building component is in a normal alarm state.
 9. A method of alarmtriggered equipment verification using drone deployment of sensors,comprising: detecting, by an alarm circuit remote from an unmannedvehicle, a failure condition of a building component; outputting, by thealarm circuit to a vehicle control circuit remote from the unmannedvehicle, an indication of the failure condition; generating, by thevehicle control circuit based on the indication of the alarm condition,an equipment verification signal that includes an identifier of thebuilding component, a position of the building component, and a test ofthe building component to be executed; and transmitting, by the vehiclecontrol circuit to a flight controller of the unmanned vehicle via acommunications circuit of the unmanned vehicle, the equipmentverification signal to cause the unmanned vehicle to execute the test ofthe building component.
 10. The method of claim 9, further comprising:executing, by a sensor circuit of the unmanned vehicle, the test of thebuilding component based on the equipment verification signal to detectsensor data regarding the building component; and transmitting, by thecommunications circuit of the unmanned vehicle, a sensor signal based onthe sensor data detected by the sensor circuit.
 11. The method of claim9, comprising: detecting, by an image capture device of the unmannedvehicle, at least one image of the building component; and transmitting,by the communications circuit of the unmanned vehicle, the at least oneimage to the vehicle control circuit.
 12. The method of claim 9,comprising: detecting, by an audio sensor, audio information regardingthe building component.
 13. The method of claim 9, comprising:analyzing, by a verification circuit, sensor data detected by a sensorcircuit of the unmanned vehicle; and generating, by the verificationcircuit based on the analyzed sensor data, a verification signalindicating whether the failure condition is verified.
 14. The method ofclaim 9, comprising: the unmanned vehicle includes at least one of atemperature sensor, an infrared sensor, a fire detector, a smokedetector, a light sensor, and a gas detector.
 15. The method of claim 9,comprising: directing, by the flight controller, the unmanned vehicle toreturn to a base station responsive to at least one of (1) completingthe test of the building component and (2) the alarm circuit indicatingthe building component is in a normal alarm state.
 16. A vehicle controlcircuit, comprising: one or more processors; and a non-transitoryprocessor-executable medium storing processor-readable instructions thatwhen executed by the one or more processors, cause the one or moreprocessors to: receive, from an alarm circuit remote from an unmannedvehicle, an indication of an alarm condition regarding a buildingcomponent; generate, based on the indication of the alarm condition, anequipment verification signal that includes an identifier of thebuilding component; and output, to a flight controller of the unmannedvehicle via a communications circuit of the unmanned vehicle, theequipment verification signal to cause the unmanned vehicle to execute atest of the building component.
 17. The vehicle control circuit of claim16, comprising instructions that cause the one or more processors to:analyze sensor data detected by a sensor circuit of the unmannedvehicle; and generate, based on the analyzed sensor data, a verificationsignal indicating whether the failure condition is verified based onexecuting the test of the building component.
 18. The vehicle controlcircuit of claim 16, comprising instructions that cause the one or moreprocessors to: set the alarm circuit to a normal alarm state responsiveto determining the failure condition to not be verified.
 19. The vehiclecontrol circuit of claim 16, comprising instructions that cause the oneor more processors to: generate the equipment verification signal toinclude a position of the building component by retrieving the positionof the building component from a database mapping the identifier of thebuilding component to the position of the building component.
 20. Thevehicle control circuit of claim 16, comprising instructions that causethe one or more processors to: generate the equipment verificationsignal to include the test of the building component to be executed byretrieving the test of the building component from a database mappingthe identifier of the building component to the test of the buildingcomponent.